Skip to content

chore: bump the cluster context pin - #39

Merged
ExtraToast merged 1 commit into
mainfrom
chore/bump-cluster-context
Aug 27, 2026
Merged

chore: bump the cluster context pin#39
ExtraToast merged 1 commit into
mainfrom
chore/bump-cluster-context

Conversation

@ExtraToast

Copy link
Copy Markdown
Contributor

Bumps the cluster context pin from e839b908 to 95dc39fc (JorisJonkers-dev/workspace#53).

Both contexts were pulled and diffed: cluster-context-public.yml and adapter-compat.yaml are byte-identical. The only substantive change is the sourceSha provenance field, 22b9d3327ee477c1.

Proven on a control first — JorisJonkers-dev/auth-ui#36 rendered with all scorecard checks passing, including context_pinned, before this went out to the rest.

Read the deploy-preview render rather than the green tick.

@ExtraToast ExtraToast added the type: chore Maintenance work without intended behavior change. label Aug 27, 2026
@ExtraToast ExtraToast self-assigned this Aug 27, 2026
@github-actions

Copy link
Copy Markdown

Deploy Preview — auth-api

Environments: production
Context ref: ghcr.io/jorisjonkers-dev/cluster-deploy-context-public@sha256:95dc39fc695694c8fb4b0c538d7fe13038d407c7302c3725c98f0496c6a83499
Workloads: 1 | Routes: 1 | Gatus endpoints: 1

Image refs

  • auth-api: ghcr.io/jorisjonkers-dev/auth-api/auth-api@sha256:0000000000000000000000000000000000000000000000000000000000000000

SC-11 Readiness Scorecard

Check Status Detail
schema_pinned pass
context_pinned pass
no_latest_images pass
health_declared pass
route_owner_authmode_declared pass
rollback_retention_acknowledged pass
no_raw_secrets pass
stateful_policy_declared not_applicable deployment declares no stateful workloads
raw_manifests_guarded not_applicable no workload enables rawManifests
npm_signatures_verified not_applicable provenance is only evaluated when publishing an artifact

pass = ready · fail = blocks deployment · not_applicable = check does not apply

➖ 3 check(s) not applicable: stateful_policy_declared, raw_manifests_guarded, npm_signatures_verified


Updated by deploy-check on push to this PR.

@ExtraToast
ExtraToast merged commit dadac9e into main Aug 27, 2026
11 checks passed
@ExtraToast
ExtraToast deleted the chore/bump-cluster-context branch August 27, 2026 08:41
ExtraToast added a commit that referenced this pull request Aug 27, 2026
My cross-repo context bump (#39) used a script that does 'git add -A',
which swept the untracked .claude/worktrees/generic-500 directory into the
commit. It went in as a gitlink - mode 160000 - because that directory
contains its own .git file.

A gitlink with no matching .gitmodules entry breaks recursive checkout:

  fatal: No url found for submodule path
  'services/auth-api/.claude/worktrees/generic-500'

Once the workspace pointer advanced to that commit, the estate's
governance-audit workflow started failing at checkout, because it clones
the workspace with --recurse-submodules.

Removes the gitlink and gitignores .claude/, which is local Claude Code
session state and should never have been committable here.

Note agent-kit deliberately commits .claude/ - it ships agents, commands,
hooks and skills - so this belongs in each repo's .gitignore rather than
the shared template.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: chore Maintenance work without intended behavior change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant